翻訳と辞書
Words near each other
・ "O" Is for Outlaw
・ "O"-Jung.Ban.Hap.
・ "Ode-to-Napoleon" hexachord
・ "Oh Yeah!" Live
・ "Our Contemporary" regional art exhibition (Leningrad, 1975)
・ "P" Is for Peril
・ "Pimpernel" Smith
・ "Polish death camp" controversy
・ "Pro knigi" ("About books")
・ "Prosopa" Greek Television Awards
・ "Pussy Cats" Starring the Walkmen
・ "Q" Is for Quarry
・ "R" Is for Ricochet
・ "R" The King (2016 film)
・ "Rags" Ragland
・ ! (album)
・ ! (disambiguation)
・ !!
・ !!!
・ !!! (album)
・ !!Destroy-Oh-Boy!!
・ !Action Pact!
・ !Arriba! La Pachanga
・ !Hero
・ !Hero (album)
・ !Kung language
・ !Oka Tokat
・ !PAUS3
・ !T.O.O.H.!
・ !Women Art Revolution


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

domain analysis : ウィキペディア英語版
domain analysis
In software engineering, domain analysis, or product line analysis, is the process of analyzing related software systems in a domain to find their common and variable parts. It is a model of wider business context for the system. The term was coined in the early 1980s by James Neighbors.〔Neighbors, J.M. (''Software Construction using Components'' ). Technical Report 160, Department of Information and Computer Sciences, University of California, Irvine, 1980.〕〔Neighbors, J.M. "The Draco Approach to Constructing Software from Reusable Components". IEEE Transactions on Software Engineering, SE-10(5), September 1984.〕 Domain analysis is the first phase of domain engineering. It is a key method for realizing systematic software reuse.〔Dennis de Champeaux, Douglas Lea, and Penelope Faure (1993). (Domain Analysis ), chapter 13, ''Object-Oriented System Development''. Rahul Wis. ISBN 0-201-56355-X.〕
Domain analysis produces domain models using methodologies such as domain specific languages, ''feature tables'', ''facet tables'', ''facet templates'', and ''generic architectures'', which describe all of the systems in a domain. Several methodologies for domain analysis have been proposed.〔Frakes, W.B. and Kyo Kang, (2005), "Software Reuse Research: Status and Future", IEEE Transactions on Software Engineering, 31(7), July, pp. 529-536.〕
The products, or "artifacts", of a domain analysis are sometimes object-oriented models (e.g. represented with the Unified Modeling Language (UML)) or data models represented with entity-relationship diagrams (ERD). Software developers can use these models as a basis for the implementation of software architectures and applications. This approach to domain analysis is sometimes called model-driven engineering.
In information science, the term "domain analysis" was suggested in 1995 by Birger Hjørland and H. Albrechtsen.〔B. Hjørland, H. Albrechtsen, "Toward a New Horizon in Information Science: Domain-Analysis", ''Journal of the American Society for Information Science'', No. 6, vol. 46 (1995), pp. 400-425〕〔(Birger Hjørland's definition of domain analysis )〕
== Domain analysis techniques ==
Several domain analysis techniques have been identified, proposed and developed due to the diversity of goals, domains, and involved processes.
* DARE: Domain Analysis and Reuse Environment (), ()
* Feature-Oriented Domain Analysis (FODA)()
* IDEF0 for Domain Analysis ()

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「domain analysis」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.